-
Notifications
You must be signed in to change notification settings - Fork 1
ROX-15718: Prepare usage of WorkflowTemplates in flavors #1553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
A single node development cluster (infra-pr-1553) was allocated in production infra for this PR. CI will attempt to deploy 🔌 You can connect to this cluster with: 🛠️ And pull infractl from the deployed dev infra-server with: 🚲 You can then use the dev infra instance e.g.: Further Development☕ If you make changes, you can commit and push and CI will take care of updating the development cluster. 🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with: LogsLogs for the development infra depending on your @redhat.com authuser: Or: |
…ge (cowsay:latest is not compatible with modern GKE), fix pod name logic to support templateRefs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 this looks great
|
With reusable WorkflowTemplates, we can refactor duplicated code between flavors, for example the
waitstep, or theopenshift-perf-scaleworkflow CR.It is also very useful if we want to make the infra flavors more flexible, e.g. by combining an empty cluster with a demo-ifyer + data seeder, as such a part could be implemented through a WorkflowTemplate with DRY principles in mind.
Other things this PR achieves:
helm-{deploy, template, diff}by sending output to stderrdocker/whalesay:latestimage is not compatible with our modern GKE versiontest-simulateis an example workflow that uses templates. During e2e testing forinfractl logs, I observed that pod names are different for template referenced steps, which I fixed in thedeterminePodNamemethod.Validation
besides e2e tests, I deployed 5965462 to https://dev.infra.rox.systems/. Feel free to play around with it.